Set up Cursor Cloud dev environment for ODF Console - #2
Set up Cursor Cloud dev environment for ODF Console#2TimothyAsirJeyasing wants to merge 1 commit into
Conversation
Co-authored-by: Timothy <tjeyasin@redhat.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
2 participants
Summary
Sets up and verifies the development environment for ODF Console (the OpenShift Data Foundation dynamic console plugin).
AGENTS.mdwith a## Cursor Cloud specific instructionssection documenting the package manager (Yarn Berry v4 via Corepack), Node runtime, standard lint/test/dev commands, and non-obvious caveats (full UI needs a live OpenShift cluster + console bridge; pre-commit hook rewriteslocales/).corepack enable+yarn install.Verification
yarn install— dependencies installed (Yarn 4.12.0 / Corepack).yarn lint— passed (eslint + stylelint).yarn test— 667 passed, 6 skipped.yarn dev— webpack dev server compiled successfully and servesplugin-manifest.json(81 extensions, HTTP 200) andplugin-entry.js(521 KB) on port 9001.Hello-world check: fetched the served
plugin-manifest.json— the exact artifact the OpenShift Console bridge loads to register the plugin.Plugin manifest served on localhost:9001
Note: running the full plugin UI requires a live OpenShift cluster + console bridge (
yarn dev:c), which is not available in the cloud VM;yarn dev(serving the bundle/manifest) is the runnable, verifiable target here.To show artifacts inline, enable in settings.